Nways Manager Version 2.1 allows you to manage devices using Java-based Management Applications (JMAs). JMAs provide device-specific management functions and operations, such as support to enable and disable device ports or to update device microcode. Nways Manager Version 2.1 includes a variety of JMAs for IBM networking hardware products. These are listed in Supported Hardware.
For the most up-to-date information on hardware supported by Nways Manager Element Manager, see our Web site at:
http://www.networking.ibm.com/netmgt
In addition to the device-specific management applications, Nways Manager Version 2.1 includes RMON Management Integration.
The first time you start an application, be sure to log in as a root user. To start the Element Manager applications that you have installed, enter the command:
/opt/OV/bin/ovw
The Network Node Manager root map is displayed, from which you can open Nways Manager applications.
The first time you start an application, be sure to log in as an administrative user. To start the Element Manager applications that you have installed, enter the command:
\opt\OV\bin\ovw
The Tivoli NetView IT Director's Edition for Windows NT or HP OpenView Network Node Manager on Windows NT map is displayed, from which you can open Nways Manager applications.
The Java-based Management application interface has four areas:
Note: | This does not apply to Telnet equipment, which will not use a secondary IP address. |
Items shown on the device graphic are the same as many items in the navigation tree, and show the same status conditions. Selecting an item on the device graphic produces the same information panel as selecting the item from the navigation tree.
If the JMA is unable to determine the device type during startup, the device view is empty, and only the navigation tree is displayed.
The Java-based Management Application Window also allows you to change the layout of the window and the colors used in the display. See the online help for information on how to do this.
The navigation tree is a hierarchical structure that enables you to view the range of management information about the managed device. This includes the status of the device and its components, the configuration options, and the fault options.
The navigation tree uses several icons to represent monitored resources:
Within each folder are items that make up part of the overall folder of information. The status indicated for a folder is calculated from the statuses of immediate dependent items. Click on the plus (+) next to a folder to see and take action on the items within the folder.
The status of a resource is indicated by the following colors:
To conserve resources and reduce processing time, you can turn off the collection of status information for some items.
Status collection can be turned on or off only for objects that are in MIB tables. To view or change the status collection setting, click on the dependent object in the navigation tree to display the object's status information window.
If status collection can be set, the leftmost column in the table is reserved for that purpose. A checkmark in the leftmost column of a row indicates that status collection is on for that object. Turn checkmarks on or off by clicking in the leftmost column of a row.
When some rows are checked and others are not, the status reported reflects only the checked rows.
For MIB tables with status, a popup menu is provided with the displayed tables. This popup menu can be accessed in two ways:
This menu allows you to turn status collection on or off, mark or unmark critical resources, and search through Monitored or Critical resources in the MIB table.
Critical Resource Monitoring enables the user to select one or more resources for which status is maintained as a critical resource. When status collection is turned on for a critical resource, a status of either Marginal or Critical is displayed as Critical (red) on the Navigation tree. The navigation tree also shows all parent objects (Ball and Folder Icons) in Critical status.
A critical resource can be Marked or Unmarked by clicking on its row. A checkmark in the column indicates the resource is marked as critical.
Note: | Status monitoring must also be enabled (a checkmark in the Status column) in order to calculate status for the resource. |
The popup menu in the Navigation tree can be used to select resources on a per panel basis for those resources not in the MIB table. This method is only enabled for resources with a Ball icon on the Navigation tree, but not included in a MIB table.
Expand folders by clicking the plus (+) next to the icon to display dependent items.
Collapse folders by clicking the minus (-) next to the icon to hide dependent items.
Double-click on the folder itself to display an information panel about the dependent item statuses that make up the folder status.
Double-click on a ball to display a detailed information panel about the selected item. Some of these information panels enable you to make configuration changes; others are display-only.
Some icons in the Navigation tree correspond to "hot spots" in the device view. To view status information for those resources, double-click on each resource's icon in the Navigation tree or on the hot spot in the device view.
The Web-based network management extensions provide access to the Element Manager Java-based management functions from Web browsers anywhere in your enterprise. When Nways Manager Element Manager is installed and configured for Web-based management, not only can you use Java-based management from the Nways Manager Element Manager workstation but you can access the Java-based functions from Web browser clients running on any platform from anywhere in your enterprise.
A couple of important points to remember:
You can organize the Web pages into any structure that suits your needs. The following are examples of how you might integrate the pages into your own server structure.
For Web-based network management, these things must be running:
Almost any Web server will work with the Element Manager. Note that your Web server does not need Java support. The Web server accesses the Nways Manager Element Manager Java code only as data. The cgilaunder.exe file must be configured as an executable file.
All Web Servers must be configured to communicate with the client on port 80, which is the default port in most Servers. The following sections define the required settings for some common Web Servers.
Add the following lines, in this order, to the file /Server_root/conf/srm.conf:
Alias /nways "/usr/CML/JMA/java/websvr" Alias /cgi/code "/usr/CML/JMA/java/websvr/code" ScriptAlias /cgi "/usr/CML/JMA/java/websvr"
Where Server_root is the directory in which Apache Websvr is installed, and usr is the directory where the Nways product is installed.
URL prefix: nways Map To Directory: /usr/CML/JMA/java/websvr URL prefix: cgi Map To Directory: /usr/CML/JMA/java/websvr
Action Request Template Replacement File Path ------ ---------------- --------------------- Pass /nways/* /usr/CML/JMA/java/websvr/* Exec /cgi/CgiLauncher* /usr/CML/JMA/java/websvr/CgiLauncher* Pass /cgi/* /usr/CML/JMA/java/websvr/*
All Web Servers must be configured to communicate with the client on port 80, which is the default port in most Servers. The following sections define the required settings for some common Web Servers.
Add the following lines, in this order, to the file \Server_root\conf\srm.conf:
Alias \nways "\Nways\java\websvr" Alias \cgi\code "\Nways\java\websvr\code" ScriptAlias \cgi "\Nways\java\websvr"
Where Server_root is the directory in which Apache Websvr is installed, and Nways is the directory where the Nways product is installed.
URL prefix: nways Map To Directory: \Nways\java\websvr URL prefix: cgi Map To Directory: \Nways\java\websvr
Action Request Template Replacement File Path ------ ---------------- --------------------- Pass \nways\* \Nways\java\websvr\* Exec \cgi\CgiLauncher* \Nways\java\websvr\CgiLauncher* Pass \cgi\* \Nways\java\websvr\*
This section provides details for configuring Web browsers to use the Element Manager. A few important points:
For a Web browser to be compatible with the Element Manager, it must have Java support at the appropriate level. The required level of Java is JDK 1.1.5 or later. The Java support will come with your browser, so you should not have to obtain and install Java separately.
Note: | If you are using Microsoft Internet Explorer Version 4.x or
5.x, then you need to update the Java Virtual Machine and RMI Patch
available by selecting other options at:
http://www.microsoft.com/windows/ie/download/default.asp |
Locating JMA help information
There are four ways to get help information for a JMA:
You can also get information on the latest upgrades to Nways Manager Element Manager by visiting our Web site at:
http://www.networking.ibm.com/netmgt